Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b820174909b178bf3ca1cca2898f90c647e352a015411936392c13769fec78c0

Tx prefix hash: 3fb5516dc178eb178ea53fffb5e9f40eb4118a93ce36969ae3dea19849ab5544
Tx public key: a873ea1e65bafea71e0d77045080e8e30e8b7f4af5cb33bb02fe3b455708fcf3
Timestamp: 1669782543 Timestamp [UCT]: 2022-11-30 04:29:03 Age [y:d:h:m:s]: 02:183:18:06:18
Block: 642144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653065 RingCT/type: yes/0
Extra: 01a873ea1e65bafea71e0d77045080e8e30e8b7f4af5cb33bb02fe3b455708fcf3021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.574149548000 dcy

stealth address amount amount idx
00: 1e677d4ad5b2db0f29931aa6726875127b835cf7e4ee96aa0d068f0770346ff2 4.574149548000 1082005 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": 642154, "vin": [ { "gen": { "height": 642144 } } ], "vout": [ { "amount": 4574149548, "target": { "key": "1e677d4ad5b2db0f29931aa6726875127b835cf7e4ee96aa0d068f0770346ff2" } } ], "extra": [ 1, 168, 115, 234, 30, 101, 186, 254, 167, 30, 13, 119, 4, 80, 128, 232, 227, 14, 139, 127, 74, 245, 203, 51, 187, 2, 254, 59, 69, 87, 8, 252, 243, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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