Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6cdca3e26c7ad6bc735bba8f5709427927ab638d954aa1d757f55e472d1e893

Tx prefix hash: f33ed958516351cf55cb8ee859f3095d9433f35c18fe3f0d1a2c8f41ad3924d5
Tx public key: bbefefca9ede03bfc9012a6a0d53c9d0b14c2c76a1d354f0b8ad38e863eec6c4
Timestamp: 1631475710 Timestamp [UCT]: 2021-09-12 19:41:50 Age [y:d:h:m:s]: 04:049:18:01:09
Block: 332496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069467 RingCT/type: yes/0
Extra: 01bbefefca9ede03bfc9012a6a0d53c9d0b14c2c76a1d354f0b8ad38e863eec6c402110000001d8d0de867000000000000000000

1 output(s) for total of 48.562738520000 dcy

stealth address amount amount idx
00: bdbc1bd01330347435512cbfb36d6cf89ee0b0787275690c710ca987be746e79 48.562738520000 686567 of 0

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": 332506, "vin": [ { "gen": { "height": 332496 } } ], "vout": [ { "amount": 48562738520, "target": { "key": "bdbc1bd01330347435512cbfb36d6cf89ee0b0787275690c710ca987be746e79" } } ], "extra": [ 1, 187, 239, 239, 202, 158, 222, 3, 191, 201, 1, 42, 106, 13, 83, 201, 208, 177, 76, 44, 118, 161, 211, 84, 240, 184, 173, 56, 232, 99, 238, 198, 196, 2, 17, 0, 0, 0, 29, 141, 13, 232, 103, 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