Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9139bcc19a83541d948568adec225032f797e7a90e45cd00483c3df6dcb858bf

Tx prefix hash: c24025e1707eda74729f40b04d33c1db6fcf8a6f96989e533f0c6e1e6ee4140b
Tx public key: 744b1e68c1ff43d0f21f965410864a3cf80c989dea8f2255a0c1d671784c62fa
Timestamp: 1704971497 Timestamp [UCT]: 2024-01-11 11:11:37 Age [y:d:h:m:s]: 01:074:23:09:01
Block: 932942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314668 RingCT/type: yes/0
Extra: 01744b1e68c1ff43d0f21f965410864a3cf80c989dea8f2255a0c1d671784c62fa0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 704a6eb59256fb28e92138bca82a5c886df1d5517cae4cba7f68a36eb7134aef 0.600000000000 1390882 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": 932952, "vin": [ { "gen": { "height": 932942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "704a6eb59256fb28e92138bca82a5c886df1d5517cae4cba7f68a36eb7134aef" } } ], "extra": [ 1, 116, 75, 30, 104, 193, 255, 67, 208, 242, 31, 150, 84, 16, 134, 74, 60, 248, 12, 152, 157, 234, 143, 34, 85, 160, 193, 214, 113, 120, 76, 98, 250, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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