Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d67d0e096d81f5df9b8b383f8c0dcb3f1adc7c04be52623ba935beed33f670

Tx prefix hash: f780653b66df73710ba263ca5ac592212b74dca49bc82ac8b33d5d53ef546129
Tx public key: 733840f94c7c85bd0db79204c9a5f201e1dce65713177b8cd7ad2ae717cbdf28
Timestamp: 1704272365 Timestamp [UCT]: 2024-01-03 08:59:25 Age [y:d:h:m:s]: 01:320:21:51:53
Block: 927166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488186 RingCT/type: yes/0
Extra: 01733840f94c7c85bd0db79204c9a5f201e1dce65713177b8cd7ad2ae717cbdf280211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d12456b428c72db36c07a1d83587016fe2f49e4752e8c13af09ae97c9facfe80 0.600000000000 1384970 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": 927176, "vin": [ { "gen": { "height": 927166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d12456b428c72db36c07a1d83587016fe2f49e4752e8c13af09ae97c9facfe80" } } ], "extra": [ 1, 115, 56, 64, 249, 76, 124, 133, 189, 13, 183, 146, 4, 201, 165, 242, 1, 225, 220, 230, 87, 19, 23, 123, 140, 215, 173, 42, 231, 23, 203, 223, 40, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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