Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c6c9bd8f15f43b9b892eeb00e859eca0c8ff5515f8dc23c83932f4f066c708

Tx prefix hash: 0c20e479e5447c3d1d31855ea1e820bb844d98937f74748ed1e612e7caee2cd0
Tx public key: 40d2f48816d9658d38e319180c586d5bd4f442e779d85ba6478cff12f9ed4369
Timestamp: 1711650682 Timestamp [UCT]: 2024-03-28 18:31:22 Age [y:d:h:m:s]: 01:194:07:26:37
Block: 988354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397494 RingCT/type: yes/0
Extra: 0140d2f48816d9658d38e319180c586d5bd4f442e779d85ba6478cff12f9ed43690211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84e2c3f6017181d4b84a81399784c11df947117dd8f36c255f5a291473c75aaa 0.600000000000 1448631 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": 988364, "vin": [ { "gen": { "height": 988354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84e2c3f6017181d4b84a81399784c11df947117dd8f36c255f5a291473c75aaa" } } ], "extra": [ 1, 64, 210, 244, 136, 22, 217, 101, 141, 56, 227, 25, 24, 12, 88, 109, 91, 212, 244, 66, 231, 121, 216, 91, 166, 71, 140, 255, 18, 249, 237, 67, 105, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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