Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b466e3da5f7394cfaf6dc893ae54ce82476337649241da62338b6600c4eed8f

Tx prefix hash: 805ad66391d876b260baea948c03ba8e82c171ed1a22224de1fc9be2fc0c57e9
Tx public key: 6bf4664173b52021495dfec90fde6fae60e02d5ce67ef2a9d231f088fdcd52b7
Timestamp: 1718008203 Timestamp [UCT]: 2024-06-10 08:30:03 Age [y:d:h:m:s]: 00:166:23:23:03
Block: 1041044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119506 RingCT/type: yes/0
Extra: 016bf4664173b52021495dfec90fde6fae60e02d5ce67ef2a9d231f088fdcd52b70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb2aa01bc9aae3a2cb0ba1155cd8499a718fe72075e2fb46d7ea50b423641c8e 0.600000000000 1509709 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": 1041054, "vin": [ { "gen": { "height": 1041044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb2aa01bc9aae3a2cb0ba1155cd8499a718fe72075e2fb46d7ea50b423641c8e" } } ], "extra": [ 1, 107, 244, 102, 65, 115, 181, 32, 33, 73, 93, 254, 201, 15, 222, 111, 174, 96, 224, 45, 92, 230, 126, 242, 169, 210, 49, 240, 136, 253, 205, 82, 183, 2, 17, 0, 0, 0, 1, 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