Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3d7d53efc81722833ff710271dfe44acb093daec00b1028e6f96bf1075a1d7b

Tx prefix hash: 539863c593cff1dbdda2576d4bc828e2f6dae848149170369ae930452037efe5
Tx public key: 9a72e6e01f5665e09dbd30b3e2c4a22aee4b8e8ed8082dcaeee831ba012075c2
Timestamp: 1708205219 Timestamp [UCT]: 2024-02-17 21:26:59 Age [y:d:h:m:s]: 01:114:03:36:15
Block: 959765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342663 RingCT/type: yes/0
Extra: 019a72e6e01f5665e09dbd30b3e2c4a22aee4b8e8ed8082dcaeee831ba012075c20211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1abdbabc8656ffc344707fe18edb548dbd4b8505a7f08f28230851c2b1c512c 0.600000000000 1419318 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": 959775, "vin": [ { "gen": { "height": 959765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1abdbabc8656ffc344707fe18edb548dbd4b8505a7f08f28230851c2b1c512c" } } ], "extra": [ 1, 154, 114, 230, 224, 31, 86, 101, 224, 157, 189, 48, 179, 226, 196, 162, 42, 238, 75, 142, 142, 216, 8, 45, 202, 238, 232, 49, 186, 1, 32, 117, 194, 2, 17, 0, 0, 0, 7, 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