Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f5936f15c478453b7c3b5535ff6f31f2a27704b915bdf3b44f3514b271bf57a

Tx prefix hash: db619e63b1b3aef8a02c00a61be48baa9fc3b4cdec9e24f3c78860beeb199287
Tx public key: c4c5f20689a7516d469e3faa3095e99e0a2f71ebaa549da6fc4e71defc788855
Timestamp: 1646526692 Timestamp [UCT]: 2022-03-06 00:31:32 Age [y:d:h:m:s]: 02:310:03:23:51
Block: 452185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 741151 RingCT/type: yes/0
Extra: 01c4c5f20689a7516d469e3faa3095e99e0a2f71ebaa549da6fc4e71defc78885502110000000406faf294000000000000000000

1 output(s) for total of 19.486043138000 dcy

stealth address amount amount idx
00: 62eb52aeeaac98b503bf8ee5d143636a823f9072a68a32b0a70e44db00f4a147 19.486043138000 867442 of 0

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": 452195, "vin": [ { "gen": { "height": 452185 } } ], "vout": [ { "amount": 19486043138, "target": { "key": "62eb52aeeaac98b503bf8ee5d143636a823f9072a68a32b0a70e44db00f4a147" } } ], "extra": [ 1, 196, 197, 242, 6, 137, 167, 81, 109, 70, 158, 63, 170, 48, 149, 233, 158, 10, 47, 113, 235, 170, 84, 157, 166, 252, 78, 113, 222, 252, 120, 136, 85, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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