Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13eede8c1aa5efad9a3a178c5cd72a875afb321dd0c4c59ad8bec600e0d85d04

Tx prefix hash: 73581cdd70f32199b3e0c32a039ae8b0657bdbd9aac957030be2102c6cb7ced5
Tx public key: f1b072010bd6e20f9e86e2275089fa0e271608bf5cf992800c70b34db5216b9a
Timestamp: 1701770559 Timestamp [UCT]: 2023-12-05 10:02:39 Age [y:d:h:m:s]: 01:129:00:44:35
Block: 906415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353376 RingCT/type: yes/0
Extra: 01f1b072010bd6e20f9e86e2275089fa0e271608bf5cf992800c70b34db5216b9a02110000000933af99f4000000000000000000

1 output(s) for total of 0.609075048000 dcy

stealth address amount amount idx
00: 37a34831ae2dfe1dc0a6fd0146666d7404f82ad136872bf88ebe32394dbf05d0 0.609075048000 1363348 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": 906425, "vin": [ { "gen": { "height": 906415 } } ], "vout": [ { "amount": 609075048, "target": { "key": "37a34831ae2dfe1dc0a6fd0146666d7404f82ad136872bf88ebe32394dbf05d0" } } ], "extra": [ 1, 241, 176, 114, 1, 11, 214, 226, 15, 158, 134, 226, 39, 80, 137, 250, 14, 39, 22, 8, 191, 92, 249, 146, 128, 12, 112, 179, 77, 181, 33, 107, 154, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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