Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8eb326c76e694a4cd418d216093945cb0915e40f4f1271bae53f37d9f01b28c

Tx prefix hash: b912423fbd50d670295e3e69cfdbc49a9b08d2974b792eb2dd5c725c14b6c106
Tx public key: e3ff66009047c48df26a1a63faf8faed608ab50b6a4c7b50dd85884a8be0f383
Timestamp: 1709951347 Timestamp [UCT]: 2024-03-09 02:29:07 Age [y:d:h:m:s]: 01:070:02:28:55
Block: 974251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311132 RingCT/type: yes/0
Extra: 01e3ff66009047c48df26a1a63faf8faed608ab50b6a4c7b50dd85884a8be0f38302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f75fa0fc15b4878f4d8b00bff9ff1bbb048751bb6b328735892ab3d49d9d15b 0.600000000000 1434206 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": 974261, "vin": [ { "gen": { "height": 974251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f75fa0fc15b4878f4d8b00bff9ff1bbb048751bb6b328735892ab3d49d9d15b" } } ], "extra": [ 1, 227, 255, 102, 0, 144, 71, 196, 141, 242, 106, 26, 99, 250, 248, 250, 237, 96, 138, 181, 11, 106, 76, 123, 80, 221, 133, 136, 74, 139, 224, 243, 131, 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