Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597b820fd097a961e68f37bc6e50328044eadaa3b7bbd51871f54440c7cbde29

Tx prefix hash: a89077b29ebf02fa54ce8200819a177a5932755d5557c5da27354e095f655872
Tx public key: 99dec70df3abea5a1110a1353ebf072b0f5a25557a4f2edddb05d4f172539f8e
Timestamp: 1722527598 Timestamp [UCT]: 2024-08-01 15:53:18 Age [y:d:h:m:s]: 00:238:21:02:55
Block: 1078506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170627 RingCT/type: yes/0
Extra: 0199dec70df3abea5a1110a1353ebf072b0f5a25557a4f2edddb05d4f172539f8e02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf4c65b1e02a48d7bcc85772711656befbffb2691babd8ea2346edb4f004a09 0.600000000000 1551085 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": 1078516, "vin": [ { "gen": { "height": 1078506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf4c65b1e02a48d7bcc85772711656befbffb2691babd8ea2346edb4f004a09" } } ], "extra": [ 1, 153, 222, 199, 13, 243, 171, 234, 90, 17, 16, 161, 53, 62, 191, 7, 43, 15, 90, 37, 85, 122, 79, 46, 221, 219, 5, 212, 241, 114, 83, 159, 142, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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