Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df0d6d88bfb161bd2d59d182b42a798b1a5edc9134467be5332ef8fe4035f1f

Tx prefix hash: a3d408d9afa00145fd122bd3a22a65564cae4a64b7b0c6ca2e8d0a4d98e25c01
Tx public key: d4f1ffa03254f47609cb638caa571a7f3df0fd98d666ad1ae71f13df3b79e8f4
Timestamp: 1696094378 Timestamp [UCT]: 2023-09-30 17:19:38 Age [y:d:h:m:s]: 01:261:13:23:42
Block: 859568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447904 RingCT/type: yes/0
Extra: 01d4f1ffa03254f47609cb638caa571a7f3df0fd98d666ad1ae71f13df3b79e8f40211000000034b8f5122000000000000000000

1 output(s) for total of 0.870751908000 dcy

stealth address amount amount idx
00: 1af107dd202099db8b2d864d70b95f7b690ba90e938e32ab10acce4dd7a66f63 0.870751908000 1313800 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": 859578, "vin": [ { "gen": { "height": 859568 } } ], "vout": [ { "amount": 870751908, "target": { "key": "1af107dd202099db8b2d864d70b95f7b690ba90e938e32ab10acce4dd7a66f63" } } ], "extra": [ 1, 212, 241, 255, 160, 50, 84, 244, 118, 9, 203, 99, 140, 170, 87, 26, 127, 61, 240, 253, 152, 214, 102, 173, 26, 231, 31, 19, 223, 59, 121, 232, 244, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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