Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a538bbb65a60454516edf24d415e2e95032f7a07db17f0b53c906dc5a1a39336

Tx prefix hash: 2b4b2268ae31c7efbe8b6061dd38c1f95572b4a293e87718dbd0677636e1a2fc
Tx public key: 5c6e125878f62de558694874cd44919a426a4bf8ab77905ee0bdf8e9556c36a7
Timestamp: 1695502706 Timestamp [UCT]: 2023-09-23 20:58:26 Age [y:d:h:m:s]: 01:206:10:52:34
Block: 854659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408621 RingCT/type: yes/0
Extra: 015c6e125878f62de558694874cd44919a426a4bf8ab77905ee0bdf8e9556c36a7021100000003faf35c9c000000000000000000

1 output(s) for total of 0.903982446000 dcy

stealth address amount amount idx
00: 1b048665a72c64d6be5393a4da99f8e92764f80805e6049575f77a23d00b74e5 0.903982446000 1308645 of 0

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": 854669, "vin": [ { "gen": { "height": 854659 } } ], "vout": [ { "amount": 903982446, "target": { "key": "1b048665a72c64d6be5393a4da99f8e92764f80805e6049575f77a23d00b74e5" } } ], "extra": [ 1, 92, 110, 18, 88, 120, 246, 45, 229, 88, 105, 72, 116, 205, 68, 145, 154, 66, 106, 75, 248, 171, 119, 144, 94, 224, 189, 248, 233, 85, 108, 54, 167, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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