Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f25c1863715755560c1fad837ab5f7714b1f69d24f37774287634e3a23bd7012

Tx prefix hash: f15b9b0e8d670e0e0229ad1d12a00f93c20ade0077ffd38c052ceb51b1ef7c2e
Tx public key: 86517b0937c898c6c02fdaa21265bb8b3e46a47e3a4db13b41ddde014e618f39
Timestamp: 1716620302 Timestamp [UCT]: 2024-05-25 06:58:22 Age [y:d:h:m:s]: 00:247:09:58:36
Block: 1029544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176821 RingCT/type: yes/0
Extra: 0186517b0937c898c6c02fdaa21265bb8b3e46a47e3a4db13b41ddde014e618f3902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83db30ba0ce9bf24fb4e4bf97c65b5f690c016f4b843dec721a419ededfccfe3 0.600000000000 1497663 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": 1029554, "vin": [ { "gen": { "height": 1029544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83db30ba0ce9bf24fb4e4bf97c65b5f690c016f4b843dec721a419ededfccfe3" } } ], "extra": [ 1, 134, 81, 123, 9, 55, 200, 152, 198, 192, 47, 218, 162, 18, 101, 187, 139, 62, 70, 164, 126, 58, 77, 177, 59, 65, 221, 222, 1, 78, 97, 143, 57, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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