Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b37623393b4252d2e72697e475e9e5dac92f34fcf350f55a56882d86f12b87ce

Tx prefix hash: f568692942b5b36c9b0e8c58c53f21f0fbcdf1ee0bd10d26efb0082a517aba9b
Tx public key: 56ab06180d422947e72ede3ea0e07a216f920df527abcfb81dfcb16abf2633b5
Timestamp: 1733345642 Timestamp [UCT]: 2024-12-04 20:54:02 Age [y:d:h:m:s]: 00:111:16:20:41
Block: 1168103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79599 RingCT/type: yes/0
Extra: 0156ab06180d422947e72ede3ea0e07a216f920df527abcfb81dfcb16abf2633b50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27ad84740440e02450ef977cfbe3725e1a17c9e9ad6d43c478da604d5ed0e214 0.600000000000 1653810 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": 1168113, "vin": [ { "gen": { "height": 1168103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27ad84740440e02450ef977cfbe3725e1a17c9e9ad6d43c478da604d5ed0e214" } } ], "extra": [ 1, 86, 171, 6, 24, 13, 66, 41, 71, 231, 46, 222, 62, 160, 224, 122, 33, 111, 146, 13, 245, 39, 171, 207, 184, 29, 252, 177, 106, 191, 38, 51, 181, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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