Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b13b6ae3253e0072f017e8dc2d22a0c5efeb5c9b1d585bcf1f632ff4af03767b

Tx prefix hash: fcb90e7c50e2827a6dac00770f54cc320c850209a343290b2640f526f511c07a
Tx public key: fea0ff5d2a3e666953bc68ceae03e1ecf1fdce9fa4e55b20ea6817fe88781f40
Timestamp: 1735653932 Timestamp [UCT]: 2024-12-31 14:05:32 Age [y:d:h:m:s]: 00:114:00:09:13
Block: 1187204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81282 RingCT/type: yes/0
Extra: 01fea0ff5d2a3e666953bc68ceae03e1ecf1fdce9fa4e55b20ea6817fe88781f4002110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d5a573f3b606b0c76a80fbd4338c399e31ea21bfd41795c91d4a95cfdaeb1b 0.600000000000 1673691 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": 1187214, "vin": [ { "gen": { "height": 1187204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d5a573f3b606b0c76a80fbd4338c399e31ea21bfd41795c91d4a95cfdaeb1b" } } ], "extra": [ 1, 254, 160, 255, 93, 42, 62, 102, 105, 83, 188, 104, 206, 174, 3, 225, 236, 241, 253, 206, 159, 164, 229, 91, 32, 234, 104, 23, 254, 136, 120, 31, 64, 2, 17, 0, 0, 0, 11, 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