Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc56b353d4dbea984045ab6c767721bd5190f08c97d44a2321a78859be1ffb34

Tx prefix hash: fe45f6627170939a02b0b892e52ee755c7ddfbf59785b0574c38d2cf058686fb
Tx public key: babde1287f21e8082c33fdf0c694a1bee8f0d3f0eb4ff99f073af6472e17c1ea
Timestamp: 1633732974 Timestamp [UCT]: 2021-10-08 22:42:54 Age [y:d:h:m:s]: 03:217:19:12:09
Block: 349406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 932786 RingCT/type: yes/0
Extra: 01babde1287f21e8082c33fdf0c694a1bee8f0d3f0eb4ff99f073af6472e17c1ea02110000000b3fc41461000000000000000000

1 output(s) for total of 42.684804876000 dcy

stealth address amount amount idx
00: 0e5d238c7ba9683f50f1d17b38ca999c0198af2b9c5fd290a526c0f8c9c48eff 42.684804876000 715377 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": 349416, "vin": [ { "gen": { "height": 349406 } } ], "vout": [ { "amount": 42684804876, "target": { "key": "0e5d238c7ba9683f50f1d17b38ca999c0198af2b9c5fd290a526c0f8c9c48eff" } } ], "extra": [ 1, 186, 189, 225, 40, 127, 33, 232, 8, 44, 51, 253, 240, 198, 148, 161, 190, 232, 240, 211, 240, 235, 79, 249, 159, 7, 58, 246, 71, 46, 23, 193, 234, 2, 17, 0, 0, 0, 11, 63, 196, 20, 97, 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