Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f151a269ea0aa1fe18d3dec7100d202b03eae465b8c8eda89b868269f78848

Tx prefix hash: 75a053f831d5a9418635522383814928c0c9ed2e7b942fbbaed59dddbfda3a9b
Tx public key: 6c77e21af8dfceab7b7897b241b586feb9510d008e8f90cf7985b8998ee2699d
Timestamp: 1708022159 Timestamp [UCT]: 2024-02-15 18:35:59 Age [y:d:h:m:s]: 01:048:22:56:56
Block: 958247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296025 RingCT/type: yes/0
Extra: 016c77e21af8dfceab7b7897b241b586feb9510d008e8f90cf7985b8998ee2699d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b9e2b8c417c5d48c2b26852e0eed811654ff1ad56db2c6d57437ebf90906714 0.600000000000 1417606 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": 958257, "vin": [ { "gen": { "height": 958247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b9e2b8c417c5d48c2b26852e0eed811654ff1ad56db2c6d57437ebf90906714" } } ], "extra": [ 1, 108, 119, 226, 26, 248, 223, 206, 171, 123, 120, 151, 178, 65, 181, 134, 254, 185, 81, 13, 0, 142, 143, 144, 207, 121, 133, 184, 153, 142, 226, 105, 157, 2, 17, 0, 0, 0, 2, 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