Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09c9bbbe65c3ff7bc69a729eb221341aad52b58ee459435b0c3cff7801caade1

Tx prefix hash: f5196a02ce7645179ae9dd6138bb7dd2b8fc35a2d16bd761452466206560656c
Tx public key: 2ff237f50e39b0f8518bdee47b7da903e7df3a254fae39fc1090768f3f2aa2cc
Timestamp: 1720351148 Timestamp [UCT]: 2024-07-07 11:19:08 Age [y:d:h:m:s]: 00:292:20:08:54
Block: 1060466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209245 RingCT/type: yes/0
Extra: 012ff237f50e39b0f8518bdee47b7da903e7df3a254fae39fc1090768f3f2aa2cc02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12d693b49537059ad5f4da6e5ac6d93b4d0549c80ca3b30b22dfdad17c0c50ce 0.600000000000 1530949 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": 1060476, "vin": [ { "gen": { "height": 1060466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12d693b49537059ad5f4da6e5ac6d93b4d0549c80ca3b30b22dfdad17c0c50ce" } } ], "extra": [ 1, 47, 242, 55, 245, 14, 57, 176, 248, 81, 139, 222, 228, 123, 125, 169, 3, 231, 223, 58, 37, 79, 174, 57, 252, 16, 144, 118, 143, 63, 42, 162, 204, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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