Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe3280a1d70e8555416c2471739e36edd211cfa305eb4f5a453827e9d9f7f955

Tx prefix hash: c76a8f8c23b6dd423c726acd94ac507664a96d67e76bdb4a11afcff52bbbf871
Tx public key: 4f1447fddecb0ff51d8c90dcbc74eb0fc616d27de20223dce5351b76a853cbc5
Timestamp: 1706612197 Timestamp [UCT]: 2024-01-30 10:56:37 Age [y:d:h:m:s]: 01:070:09:26:25
Block: 946546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311378 RingCT/type: yes/0
Extra: 014f1447fddecb0ff51d8c90dcbc74eb0fc616d27de20223dce5351b76a853cbc502110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37bd3c7f56184c66b1374193c4a5ba281361f0ba021735543dc659311d2cee9d 0.600000000000 1404878 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": 946556, "vin": [ { "gen": { "height": 946546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37bd3c7f56184c66b1374193c4a5ba281361f0ba021735543dc659311d2cee9d" } } ], "extra": [ 1, 79, 20, 71, 253, 222, 203, 15, 245, 29, 140, 144, 220, 188, 116, 235, 15, 198, 22, 210, 125, 226, 2, 35, 220, 229, 53, 27, 118, 168, 83, 203, 197, 2, 17, 0, 0, 0, 16, 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