Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3f69e1e26751023b9428934a8152a943826412c54fbe9aeb6a16eed5d8089d

Tx prefix hash: 6967367bf3fe8c410e79d87ffa76ded30df64d814fe5564f45fb07e1872a4616
Tx public key: b8887fb20d1e32937368677d5a54b4fa8e4be8b48aea933c0a7381bff806b782
Timestamp: 1721378765 Timestamp [UCT]: 2024-07-19 08:46:05 Age [y:d:h:m:s]: 00:300:11:19:25
Block: 1068999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214676 RingCT/type: yes/0
Extra: 01b8887fb20d1e32937368677d5a54b4fa8e4be8b48aea933c0a7381bff806b782021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3424e44a992334224479b30eb15c30690a4b4970d5963fb68698a095d2cc8c94 0.600000000000 1540250 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": 1069009, "vin": [ { "gen": { "height": 1068999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3424e44a992334224479b30eb15c30690a4b4970d5963fb68698a095d2cc8c94" } } ], "extra": [ 1, 184, 136, 127, 178, 13, 30, 50, 147, 115, 104, 103, 125, 90, 84, 180, 250, 142, 75, 232, 180, 138, 234, 147, 60, 10, 115, 129, 191, 248, 6, 183, 130, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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