Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1230bb089b938534c3acdda10f463e6cf61db382bec4051d0825512c3cc91bc4

Tx prefix hash: 4ecb8a294d868157215b0797eee9bc3e888423d748fecc026aa7a38d24cb0d7d
Tx public key: d7596017e83b01b3a36bf94936cacbf70825c67107bbf8b06baaf91c933d64f0
Timestamp: 1700378409 Timestamp [UCT]: 2023-11-19 07:20:09 Age [y:d:h:m:s]: 01:101:06:28:38
Block: 894881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333525 RingCT/type: yes/0
Extra: 01d7596017e83b01b3a36bf94936cacbf70825c67107bbf8b06baaf91c933d64f002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.665101236000 dcy

stealth address amount amount idx
00: 6b3fc324a50ac645bcfd941f415a5a423c9b703a832067a55cf723082576da13 0.665101236000 1351094 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": 894891, "vin": [ { "gen": { "height": 894881 } } ], "vout": [ { "amount": 665101236, "target": { "key": "6b3fc324a50ac645bcfd941f415a5a423c9b703a832067a55cf723082576da13" } } ], "extra": [ 1, 215, 89, 96, 23, 232, 59, 1, 179, 163, 107, 249, 73, 54, 202, 203, 247, 8, 37, 198, 113, 7, 187, 248, 176, 107, 170, 249, 28, 147, 61, 100, 240, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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