Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ecb82617c841eab2d11dacb4b3f447c356585fba24083518e1f7497d81cefe

Tx prefix hash: ec2d3c55bbcc295a6ddd268233ab29527e7681dd9509336ef6fdf648cd1599c7
Tx public key: 8f98a77c979df94946ff3ed20984f780d60fb6fd0fb21e8785bc93a22da3a515
Timestamp: 1716912058 Timestamp [UCT]: 2024-05-28 16:00:58 Age [y:d:h:m:s]: 00:323:14:16:44
Block: 1031973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231266 RingCT/type: yes/0
Extra: 018f98a77c979df94946ff3ed20984f780d60fb6fd0fb21e8785bc93a22da3a51502110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b507d699c2379ee7a21ade4344a28b3a2b59e21b3b263ce947aa417cef117579 0.600000000000 1500422 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": 1031983, "vin": [ { "gen": { "height": 1031973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b507d699c2379ee7a21ade4344a28b3a2b59e21b3b263ce947aa417cef117579" } } ], "extra": [ 1, 143, 152, 167, 124, 151, 157, 249, 73, 70, 255, 62, 210, 9, 132, 247, 128, 214, 15, 182, 253, 15, 178, 30, 135, 133, 188, 147, 162, 45, 163, 165, 21, 2, 17, 0, 0, 0, 10, 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