Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a735e093b71032f3baf663dfb2b8fa6b60afc9add7be6563362b0e1640e52a7d

Tx prefix hash: 5be4bc1e0832f845d384b4eb7f980a71e27d6f9b58e9ed85d5374393d5520d88
Tx public key: 616dfaac15127d6a33511ca87f534cb67d67d0e52803dd69a98401d41da8233d
Timestamp: 1700160066 Timestamp [UCT]: 2023-11-16 18:41:06 Age [y:d:h:m:s]: 01:065:17:23:53
Block: 893073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308332 RingCT/type: yes/0
Extra: 01616dfaac15127d6a33511ca87f534cb67d67d0e52803dd69a98401d41da8233d02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.674339209000 dcy

stealth address amount amount idx
00: 9b7052c3a3a347f3f0ea2aa53bc288e8e4325f056fb533065a5c1cb1919d22cc 0.674339209000 1349236 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": 893083, "vin": [ { "gen": { "height": 893073 } } ], "vout": [ { "amount": 674339209, "target": { "key": "9b7052c3a3a347f3f0ea2aa53bc288e8e4325f056fb533065a5c1cb1919d22cc" } } ], "extra": [ 1, 97, 109, 250, 172, 21, 18, 125, 106, 51, 81, 28, 168, 127, 83, 76, 182, 125, 103, 208, 229, 40, 3, 221, 105, 169, 132, 1, 212, 29, 168, 35, 61, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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