Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d413546647a14b80b52830bd9e93c8fdf18196831f71bbe641a283fd087a9acf

Tx prefix hash: 0ab67aff3c009fa12e8ae7faade3d4d5addc3b725e94ce65b20593920a7ff1f8
Tx public key: 0ba06a2ded0c6ae8c7dc4bef71c4820695661e77961c01105db4be118525b937
Timestamp: 1681568187 Timestamp [UCT]: 2023-04-15 14:16:27 Age [y:d:h:m:s]: 02:062:06:47:38
Block: 739176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566608 RingCT/type: yes/0
Extra: 010ba06a2ded0c6ae8c7dc4bef71c4820695661e77961c01105db4be118525b9370211000000015029cbac000000000000000000

1 output(s) for total of 2.181741459000 dcy

stealth address amount amount idx
00: 55bcf0d260b295147dc4fd684646b22fd0c3db05a84f86eda61a2df49d91613a 2.181741459000 1186001 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": 739186, "vin": [ { "gen": { "height": 739176 } } ], "vout": [ { "amount": 2181741459, "target": { "key": "55bcf0d260b295147dc4fd684646b22fd0c3db05a84f86eda61a2df49d91613a" } } ], "extra": [ 1, 11, 160, 106, 45, 237, 12, 106, 232, 199, 220, 75, 239, 113, 196, 130, 6, 149, 102, 30, 119, 150, 28, 1, 16, 93, 180, 190, 17, 133, 37, 185, 55, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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