Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a6eea284765d5427687f443b3a51a650d3433b05fe8eb9655264642f5bebce

Tx prefix hash: 38d4c60ac01a19ecd94eac4d2a879c48853fd0b3ad06d632fcb7e5ce24bf5db1
Tx public key: 57c8d267156bdf53dcab980ae0c02def153a9ff11133203e9dbd2c3fc66f0350
Timestamp: 1735578278 Timestamp [UCT]: 2024-12-30 17:04:38 Age [y:d:h:m:s]: 00:307:03:58:54
Block: 1186568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217032 RingCT/type: yes/0
Extra: 0157c8d267156bdf53dcab980ae0c02def153a9ff11133203e9dbd2c3fc66f0350021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cc83dfcc8f8988bb5e69f852c5b06f3ccd00899d9dfc4c52a4727b2ab88d049 0.600000000000 1673051 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": 1186578, "vin": [ { "gen": { "height": 1186568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cc83dfcc8f8988bb5e69f852c5b06f3ccd00899d9dfc4c52a4727b2ab88d049" } } ], "extra": [ 1, 87, 200, 210, 103, 21, 107, 223, 83, 220, 171, 152, 10, 224, 192, 45, 239, 21, 58, 159, 241, 17, 51, 32, 62, 157, 189, 44, 63, 198, 111, 3, 80, 2, 17, 0, 0, 0, 3, 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