Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fffe531d4f5c3499b112507ea52e5446b5716774df4d1211ffd478566619f6

Tx prefix hash: 79a6309de5e9f73af321969e518ccbdf2fcbfc75a14db6d71ce016e9569fe9be
Tx public key: 3fe95d5dc0d3d9d6c6881858d39e2f53545711b2415a6899a6a921a430eec382
Timestamp: 1736746411 Timestamp [UCT]: 2025-01-13 05:33:31 Age [y:d:h:m:s]: 00:087:09:31:07
Block: 1196244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62249 RingCT/type: yes/0
Extra: 013fe95d5dc0d3d9d6c6881858d39e2f53545711b2415a6899a6a921a430eec382021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71dac46d695a5db26862ced86010c4ba08501058f3677765909ae249669a9e78 0.600000000000 1682841 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": 1196254, "vin": [ { "gen": { "height": 1196244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71dac46d695a5db26862ced86010c4ba08501058f3677765909ae249669a9e78" } } ], "extra": [ 1, 63, 233, 93, 93, 192, 211, 217, 214, 198, 136, 24, 88, 211, 158, 47, 83, 84, 87, 17, 178, 65, 90, 104, 153, 166, 169, 33, 164, 48, 238, 195, 130, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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