Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31c81f188943f925494ea8915e4f7f872b1f66537c9001fe6b5842e8397b610f

Tx prefix hash: cf41f0f3a2d0cc301c62280c56563f869cc80809ab0fbc9bf60decb3af38506c
Tx public key: 8d50a0e382756246c7b2d8765299bb264a5c27341e88865b369ea7a1c13cae3c
Timestamp: 1703975756 Timestamp [UCT]: 2023-12-30 22:35:56 Age [y:d:h:m:s]: 01:145:19:52:10
Block: 924700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365366 RingCT/type: yes/0
Extra: 018d50a0e382756246c7b2d8765299bb264a5c27341e88865b369ea7a1c13cae3c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 886787490329fe7dd210336c9ea671f4967e862bbc207918c299c11fb3d9ecef 0.600000000000 1382456 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": 924710, "vin": [ { "gen": { "height": 924700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "886787490329fe7dd210336c9ea671f4967e862bbc207918c299c11fb3d9ecef" } } ], "extra": [ 1, 141, 80, 160, 227, 130, 117, 98, 70, 199, 178, 216, 118, 82, 153, 187, 38, 74, 92, 39, 52, 30, 136, 134, 91, 54, 158, 167, 161, 193, 60, 174, 60, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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