Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcdb5b49b10906c6514c2884c73fd7e5a5e5907420a67f6d36e21c88f1b86e4

Tx prefix hash: a61214a246d8603849a74c44071e083f541c0b8657ff99991f677988a95949bc
Tx public key: f8579a412ac2c565b916fee5f16fe376e15aded8420ad6c823a559094ad65e9c
Timestamp: 1719421652 Timestamp [UCT]: 2024-06-26 17:07:32 Age [y:d:h:m:s]: 01:134:19:07:59
Block: 1052751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354884 RingCT/type: yes/0
Extra: 01f8579a412ac2c565b916fee5f16fe376e15aded8420ad6c823a559094ad65e9c021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac72240bccf55c86f0eb5280f61098a01e529b243f57da6cc988c139e5f33dfa 0.600000000000 1523084 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": 1052761, "vin": [ { "gen": { "height": 1052751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac72240bccf55c86f0eb5280f61098a01e529b243f57da6cc988c139e5f33dfa" } } ], "extra": [ 1, 248, 87, 154, 65, 42, 194, 197, 101, 185, 22, 254, 229, 241, 111, 227, 118, 225, 90, 222, 216, 66, 10, 214, 200, 35, 165, 89, 9, 74, 214, 94, 156, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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