Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b124abae374a447206bfe8057bca9682634d1040bdbee944a53603ed5042ab8

Tx prefix hash: be5af49f80f4fddd5f5659d65b101d8c30b7539c5b35fe77bad082c487a6339a
Tx public key: 3d13fb09af29c6d126541b5e4c5c3fcfe5065da9f87efe36e3a294ce057c4c60
Timestamp: 1656763481 Timestamp [UCT]: 2022-07-02 12:04:41 Age [y:d:h:m:s]: 02:336:19:36:59
Block: 535017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761896 RingCT/type: yes/0
Extra: 013d13fb09af29c6d126541b5e4c5c3fcfe5065da9f87efe36e3a294ce057c4c6002110000000175e3f0e9000000000000000000

1 output(s) for total of 10.357781306000 dcy

stealth address amount amount idx
00: 6b7c3e39c75d23fa3a991d7a92f0d8a427a457e5dfb537144f78c7156d3d7b4f 10.357781306000 964608 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": 535027, "vin": [ { "gen": { "height": 535017 } } ], "vout": [ { "amount": 10357781306, "target": { "key": "6b7c3e39c75d23fa3a991d7a92f0d8a427a457e5dfb537144f78c7156d3d7b4f" } } ], "extra": [ 1, 61, 19, 251, 9, 175, 41, 198, 209, 38, 84, 27, 94, 76, 92, 63, 207, 229, 6, 93, 169, 248, 126, 254, 54, 227, 162, 148, 206, 5, 124, 76, 96, 2, 17, 0, 0, 0, 1, 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