Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 615fc67fcbe820c471e250ca5214504ae1570f7e9a74737706b5b4696b443f27

Tx prefix hash: 7b45be28abda0514f958b2cc670e8e446c235a330f718ab4e441714943eae5c0
Tx public key: bb3febc65a21e3a145b7c7722527ca9d4358b4736d03e6e4a2b3d4f63f74f3cd
Timestamp: 1733700896 Timestamp [UCT]: 2024-12-08 23:34:56 Age [y:d:h:m:s]: 00:110:15:02:37
Block: 1171060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78837 RingCT/type: yes/0
Extra: 01bb3febc65a21e3a145b7c7722527ca9d4358b4736d03e6e4a2b3d4f63f74f3cd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd4d9a845db753ecb884fc5964ea77a939a66746eaabbf2568ec26bad9ff0b1d 0.600000000000 1656795 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": 1171070, "vin": [ { "gen": { "height": 1171060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd4d9a845db753ecb884fc5964ea77a939a66746eaabbf2568ec26bad9ff0b1d" } } ], "extra": [ 1, 187, 63, 235, 198, 90, 33, 227, 161, 69, 183, 199, 114, 37, 39, 202, 157, 67, 88, 180, 115, 109, 3, 230, 228, 162, 179, 212, 246, 63, 116, 243, 205, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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