Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b296d76c8931dc8e67d6775a5ba306c8c5d6268d2a32187a65d69cf04bf486a4

Tx prefix hash: f0f9fad6fd62ae0322746a9ebd29b8b824b3f2b384b12d4821a3b7af7ddf3e76
Tx public key: 65f905f76af1803c76d77f4597f8200f5b96c1dcbca5c31c5a8b5023f4eef1f2
Timestamp: 1638781096 Timestamp [UCT]: 2021-12-06 08:58:16 Age [y:d:h:m:s]: 03:034:23:12:00
Block: 389557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803906 RingCT/type: yes/0
Extra: 0165f905f76af1803c76d77f4597f8200f5b96c1dcbca5c31c5a8b5023f4eef1f2021100000004d6e4826b000000000000000000

1 output(s) for total of 31.422180058000 dcy

stealth address amount amount idx
00: a20bc183d3ef91cfaf6ebbed1369638c4e853789d72654da7707e71aef4fac08 31.422180058000 784768 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": 389567, "vin": [ { "gen": { "height": 389557 } } ], "vout": [ { "amount": 31422180058, "target": { "key": "a20bc183d3ef91cfaf6ebbed1369638c4e853789d72654da7707e71aef4fac08" } } ], "extra": [ 1, 101, 249, 5, 247, 106, 241, 128, 60, 118, 215, 127, 69, 151, 248, 32, 15, 91, 150, 193, 220, 188, 165, 195, 28, 90, 139, 80, 35, 244, 238, 241, 242, 2, 17, 0, 0, 0, 4, 214, 228, 130, 107, 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