Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f6b59b12f8df6e22d13318de4f263f943ee895137e9c063025e207beda9a615

Tx prefix hash: a453361aa6d6d71c896cd1fc6a8a60df1c6f1aa6b8b30d0280b70bb1527f0e83
Tx public key: 5d12b67e0191fcfc44f243f5fe3b4bc37080440e1754a7c7b15567d570c020d4
Timestamp: 1706999326 Timestamp [UCT]: 2024-02-03 22:28:46 Age [y:d:h:m:s]: 01:276:20:41:11
Block: 949754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456649 RingCT/type: yes/0
Extra: 015d12b67e0191fcfc44f243f5fe3b4bc37080440e1754a7c7b15567d570c020d402110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c86bdd01653f7dae8a95f58a84ad5d76c8f628d27c1e2de901e789fd11543c50 0.600000000000 1408286 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": 949764, "vin": [ { "gen": { "height": 949754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c86bdd01653f7dae8a95f58a84ad5d76c8f628d27c1e2de901e789fd11543c50" } } ], "extra": [ 1, 93, 18, 182, 126, 1, 145, 252, 252, 68, 242, 67, 245, 254, 59, 75, 195, 112, 128, 68, 14, 23, 84, 167, 199, 177, 85, 103, 213, 112, 192, 32, 212, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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