Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72fae631875e5ed262fc4de3c46d3ce18120109153f5979ddd12557a54bdf6de

Tx prefix hash: 4f516c6151d01893a12359cd37ee7e02b48e4d59f53793a10a6f9ca184c5dba7
Tx public key: 09fea0f46ec2ff6f55bd3d389116a3afb36d9be0d52564d3ad9d70b10c9a7ca9
Timestamp: 1711100649 Timestamp [UCT]: 2024-03-22 09:44:09 Age [y:d:h:m:s]: 01:035:03:12:26
Block: 983795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286086 RingCT/type: yes/0
Extra: 0109fea0f46ec2ff6f55bd3d389116a3afb36d9be0d52564d3ad9d70b10c9a7ca902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 960ed7fddc3dcfc19473ccb2bfe886f3654efdc296038d39f76a68149a85d827 0.600000000000 1443942 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": 983805, "vin": [ { "gen": { "height": 983795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "960ed7fddc3dcfc19473ccb2bfe886f3654efdc296038d39f76a68149a85d827" } } ], "extra": [ 1, 9, 254, 160, 244, 110, 194, 255, 111, 85, 189, 61, 56, 145, 22, 163, 175, 179, 109, 155, 224, 213, 37, 100, 211, 173, 157, 112, 177, 12, 154, 124, 169, 2, 17, 0, 0, 0, 4, 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