Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356fc65b682e2b063b8fea4261dde9e180fbb72927cdc0ccfe9a72d2e36fc45f

Tx prefix hash: 954013518176459d58b4dc40015d71c42a278c926e31ede323157d176d8f53c8
Tx public key: d1179d078b24750eb88610d46500391295e27829cd03e0e3957f6b1fd23f5afc
Timestamp: 1699591717 Timestamp [UCT]: 2023-11-10 04:48:37 Age [y:d:h:m:s]: 01:131:03:14:46
Block: 888367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354921 RingCT/type: yes/0
Extra: 01d1179d078b24750eb88610d46500391295e27829cd03e0e3957f6b1fd23f5afc021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.698990625000 dcy

stealth address amount amount idx
00: 1a9e58b36542db5e560f31fa2048f8b4ff61f0de01ce9a9e08313c94f5ace913 0.698990625000 1344306 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": 888377, "vin": [ { "gen": { "height": 888367 } } ], "vout": [ { "amount": 698990625, "target": { "key": "1a9e58b36542db5e560f31fa2048f8b4ff61f0de01ce9a9e08313c94f5ace913" } } ], "extra": [ 1, 209, 23, 157, 7, 139, 36, 117, 14, 184, 134, 16, 212, 101, 0, 57, 18, 149, 226, 120, 41, 205, 3, 224, 227, 149, 127, 107, 31, 210, 63, 90, 252, 2, 17, 0, 0, 0, 3, 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