Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b4834a220f1083d23333a420f3cf68a1955eddc161af601f4f5daa13b488eb8

Tx prefix hash: 7861ae6c7ba0a8ff850b80f6bc6b9da9701ff3c82b8199d05b5191dcf221d7d9
Tx public key: 71cbf3e167993cde02168dd1fb7d7db68e6a2fef52f0e8bc9e6238ede4acdb78
Timestamp: 1735708501 Timestamp [UCT]: 2025-01-01 05:15:01 Age [y:d:h:m:s]: 00:098:23:12:48
Block: 1187649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70527 RingCT/type: yes/0
Extra: 0171cbf3e167993cde02168dd1fb7d7db68e6a2fef52f0e8bc9e6238ede4acdb78021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d33d2394a839c002a2a26a71fad3cbb1ac1bc1e550bfafa08eabe96be4e60efa 0.600000000000 1674142 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": 1187659, "vin": [ { "gen": { "height": 1187649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d33d2394a839c002a2a26a71fad3cbb1ac1bc1e550bfafa08eabe96be4e60efa" } } ], "extra": [ 1, 113, 203, 243, 225, 103, 153, 60, 222, 2, 22, 141, 209, 251, 125, 125, 182, 142, 106, 47, 239, 82, 240, 232, 188, 158, 98, 56, 237, 228, 172, 219, 120, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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