Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 25e80c28edadaea267d7667ff018e1aefe98a60bda965793a8d61185b6004fd5

Tx prefix hash: 71e1951aa9ecdda7506e9256dc6458426266d51f805082cc8e8a6c22380c27ec
Tx public key: d56a26fd6c920c9a3fd10dac1161386b5bda5b294a9a648312cf78a108dbace8
Timestamp: 1729532989 Timestamp [UCT]: 2024-10-21 17:49:49 Age [y:d:h:m:s]: 01:027:15:29:15
Block: 1136552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278162 RingCT/type: yes/0
Extra: 01d56a26fd6c920c9a3fd10dac1161386b5bda5b294a9a648312cf78a108dbace8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e115235aa08da6315a1759cd3a8d7cdbd17fb8bb894d66530d8b13569a4785e5 0.600000000000 1619899 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1136562, "vin": [ { "gen": { "height": 1136552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e115235aa08da6315a1759cd3a8d7cdbd17fb8bb894d66530d8b13569a4785e5" } } ], "extra": [ 1, 213, 106, 38, 253, 108, 146, 12, 154, 63, 209, 13, 172, 17, 97, 56, 107, 91, 218, 91, 41, 74, 154, 100, 131, 18, 207, 120, 161, 8, 219, 172, 232, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8