Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364d1804e3e4477782c8e639ef51e288b353d09d58db47d215732e99dbd15ddc

Tx prefix hash: 7ec7ac13ba3aca87ee918f6879f4659e3e3497a10e18780d6f58b0a0b1da8281
Tx public key: a778bc0b61ef0d7cac841f6afaaa03b8e848f249b066a0c81ce52ebc95c2411f
Timestamp: 1703565289 Timestamp [UCT]: 2023-12-26 04:34:49 Age [y:d:h:m:s]: 01:112:08:34:07
Block: 921302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341424 RingCT/type: yes/0
Extra: 01a778bc0b61ef0d7cac841f6afaaa03b8e848f249b066a0c81ce52ebc95c2411f021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803c7eaed35ffab8d22964bec881d5c72d4e02048a946ebca967a6ffb663e027 0.600000000000 1378988 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": 921312, "vin": [ { "gen": { "height": 921302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803c7eaed35ffab8d22964bec881d5c72d4e02048a946ebca967a6ffb663e027" } } ], "extra": [ 1, 167, 120, 188, 11, 97, 239, 13, 124, 172, 132, 31, 106, 250, 170, 3, 184, 232, 72, 242, 73, 176, 102, 160, 200, 28, 229, 46, 188, 149, 194, 65, 31, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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