Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46ef5eabb4dfd8b8e92d2d90e4a30c424f8ec837ded802bc66c3406bff835f76

Tx prefix hash: d747be251ea357a8d079e9586791e50b812125454738504ca00bfcfc43b3c7e5
Tx public key: f49581a6e0c2854cfbba60fbdc7bb7221e5a1bd63d8a71561c3f5776d340770c
Timestamp: 1709452813 Timestamp [UCT]: 2024-03-03 08:00:13 Age [y:d:h:m:s]: 01:251:13:09:53
Block: 970123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438504 RingCT/type: yes/0
Extra: 01f49581a6e0c2854cfbba60fbdc7bb7221e5a1bd63d8a71561c3f5776d340770c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b46c3f1262f2cfdd6f4c56fc19b19aa86f411eced00faffad3c2f4a0d0163a 0.600000000000 1429972 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": 970133, "vin": [ { "gen": { "height": 970123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b46c3f1262f2cfdd6f4c56fc19b19aa86f411eced00faffad3c2f4a0d0163a" } } ], "extra": [ 1, 244, 149, 129, 166, 224, 194, 133, 76, 251, 186, 96, 251, 220, 123, 183, 34, 30, 90, 27, 214, 61, 138, 113, 86, 28, 63, 87, 118, 211, 64, 119, 12, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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