Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d36719c5f179195c65a17cbeefeb5b07d2c567e1c81c3f4ebc47d1dfcb513a7

Tx prefix hash: 7d38389376e8212ebdf85c90a5861f366b3f786fb6abc7a394231be669d62e9a
Tx public key: 099fccdfdd8045dd9175c6483509d75921e8ff6c4b74892542268ea6904020d7
Timestamp: 1730770653 Timestamp [UCT]: 2024-11-05 01:37:33 Age [y:d:h:m:s]: 00:144:10:27:09
Block: 1146756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103069 RingCT/type: yes/0
Extra: 01099fccdfdd8045dd9175c6483509d75921e8ff6c4b74892542268ea6904020d7021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c852705a74db831dc018e473791b26fca91a46f7786bbcf4256e10b8fbbf257 0.600000000000 1631447 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": 1146766, "vin": [ { "gen": { "height": 1146756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c852705a74db831dc018e473791b26fca91a46f7786bbcf4256e10b8fbbf257" } } ], "extra": [ 1, 9, 159, 204, 223, 221, 128, 69, 221, 145, 117, 198, 72, 53, 9, 215, 89, 33, 232, 255, 108, 75, 116, 137, 37, 66, 38, 142, 166, 144, 64, 32, 215, 2, 17, 0, 0, 0, 6, 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