Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7144b8babb7d3d524393d4646552b2e25c4e54d5ec551f9a2d91cf51282151ee

Tx prefix hash: c599438c93e53a2a1e61a95c8a44b168f6161cf2c760a5786682b63ed743cce1
Tx public key: 02a41fa60e5a5ebb343b8dc169f5901c1fe13be05ae65c01cde5784898679e22
Timestamp: 1702115553 Timestamp [UCT]: 2023-12-09 09:52:33 Age [y:d:h:m:s]: 01:038:16:20:36
Block: 909279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289013 RingCT/type: yes/0
Extra: 0102a41fa60e5a5ebb343b8dc169f5901c1fe13be05ae65c01cde5784898679e2202110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a58d86a5fb3d82936c7b296edb2e7922de1df2266ac984ced26c1eb63b382f26 0.600000000000 1366350 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": 909289, "vin": [ { "gen": { "height": 909279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a58d86a5fb3d82936c7b296edb2e7922de1df2266ac984ced26c1eb63b382f26" } } ], "extra": [ 1, 2, 164, 31, 166, 14, 90, 94, 187, 52, 59, 141, 193, 105, 245, 144, 28, 31, 225, 59, 224, 90, 230, 92, 1, 205, 229, 120, 72, 152, 103, 158, 34, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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