Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9411bbfa7767bfcfc7d8cde4d38a870378fc2c1ad6599a42c815e4b108224e3e

Tx prefix hash: d6945cdbf4e21697c35e59e433f975ea35568400a8f37c02d7f665e1e96c706f
Tx public key: f7b07553e8ba6a0408e3186c31bfa630a442b04ee1fe5a4e46014a633781b5ed
Timestamp: 1709259031 Timestamp [UCT]: 2024-03-01 02:10:31 Age [y:d:h:m:s]: 01:036:14:40:11
Block: 968513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287159 RingCT/type: yes/0
Extra: 01f7b07553e8ba6a0408e3186c31bfa630a442b04ee1fe5a4e46014a633781b5ed02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ceea2bde132a8effc96ca92d4ff55c5f74fdbf99a57116a8c655b536865234f 0.600000000000 1428328 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": 968523, "vin": [ { "gen": { "height": 968513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ceea2bde132a8effc96ca92d4ff55c5f74fdbf99a57116a8c655b536865234f" } } ], "extra": [ 1, 247, 176, 117, 83, 232, 186, 106, 4, 8, 227, 24, 108, 49, 191, 166, 48, 164, 66, 176, 78, 225, 254, 90, 78, 70, 1, 74, 99, 55, 129, 181, 237, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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