Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 872ed39cb4589048020a799e1ef1fb5397cd440e07ab0cd9cde2d28035bacb73

Tx prefix hash: 016f3868221c40e2cb08aea39701c6bb55fb6f47e4288599c19634d45a70ea50
Tx public key: 3e087806d0e8ee224e59fe8e31849e27cf3485c979dc9d54c7d6bf49e1852a93
Timestamp: 1714376221 Timestamp [UCT]: 2024-04-29 07:37:01 Age [y:d:h:m:s]: 00:346:13:29:35
Block: 1010931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247737 RingCT/type: yes/0
Extra: 013e087806d0e8ee224e59fe8e31849e27cf3485c979dc9d54c7d6bf49e1852a9302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23a99cc5159c8ffac89a4d4e1d2606b9ebf531ad152a7462b5bccd764790b67b 0.600000000000 1473017 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": 1010941, "vin": [ { "gen": { "height": 1010931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23a99cc5159c8ffac89a4d4e1d2606b9ebf531ad152a7462b5bccd764790b67b" } } ], "extra": [ 1, 62, 8, 120, 6, 208, 232, 238, 34, 78, 89, 254, 142, 49, 132, 158, 39, 207, 52, 133, 201, 121, 220, 157, 84, 199, 214, 191, 73, 225, 133, 42, 147, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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