Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c839a27eb6f470f43ce3f95ed4cf2cb59eea1fbda2a67cca91d886df66a76ee6

Tx prefix hash: 7546df41083f6941829b543f214b2008fb6d317adc084585e3b8326ca0d6060a
Tx public key: 9675fe304e0049980756a6d4b0dd8eb2f23dc1d9d107fda642c369b7bf544041
Timestamp: 1698241689 Timestamp [UCT]: 2023-10-25 13:48:09 Age [y:d:h:m:s]: 01:146:15:02:37
Block: 877384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365803 RingCT/type: yes/0
Extra: 019675fe304e0049980756a6d4b0dd8eb2f23dc1d9d107fda642c369b7bf544041021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.760085776000 dcy

stealth address amount amount idx
00: 303193ada05c45d64a179f757d8abb0ce1fb5047d4186c402060e1f4641d07cd 0.760085776000 1332758 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": 877394, "vin": [ { "gen": { "height": 877384 } } ], "vout": [ { "amount": 760085776, "target": { "key": "303193ada05c45d64a179f757d8abb0ce1fb5047d4186c402060e1f4641d07cd" } } ], "extra": [ 1, 150, 117, 254, 48, 78, 0, 73, 152, 7, 86, 166, 212, 176, 221, 142, 178, 242, 61, 193, 217, 209, 7, 253, 166, 66, 195, 105, 183, 191, 84, 64, 65, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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