Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a13e0124d56ee7abdd6c1f4ff61791897b2637a71f3c2f82691f192b7c5fa73f

Tx prefix hash: 30c7b33ed392a574464a074f1a5b93800d643c363e5760105c5b4ef136fd2c2e
Tx public key: e541336395003f458b2f32b99d65b538c8227fcccd88d431f739a48e6851f5c2
Timestamp: 1728788338 Timestamp [UCT]: 2024-10-13 02:58:58 Age [y:d:h:m:s]: 00:152:23:01:57
Block: 1130417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109115 RingCT/type: yes/0
Extra: 01e541336395003f458b2f32b99d65b538c8227fcccd88d431f739a48e6851f5c2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dce12220828c7f08d9e834d82d162070e02640f7fcfc027b4759a6852c5d042e 0.600000000000 1613294 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": 1130427, "vin": [ { "gen": { "height": 1130417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dce12220828c7f08d9e834d82d162070e02640f7fcfc027b4759a6852c5d042e" } } ], "extra": [ 1, 229, 65, 51, 99, 149, 0, 63, 69, 139, 47, 50, 185, 157, 101, 181, 56, 200, 34, 127, 204, 205, 136, 212, 49, 247, 57, 164, 142, 104, 81, 245, 194, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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