Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7c4c3a7f6645689b2f77b5b8ad303fbcf425e817b67249050b6df5f0f97024

Tx prefix hash: 632ac6e1eb5023e7ee8b0c789e41c8696d2686a050fa5b28071f8bc097566a35
Tx public key: 8edc086fabab74cc18cbbcfd79cd3340d422ef8a6c592700dcc7784225af9a3c
Timestamp: 1634976855 Timestamp [UCT]: 2021-10-23 08:14:15 Age [y:d:h:m:s]: 03:072:08:15:24
Block: 358688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 830017 RingCT/type: yes/0
Extra: 018edc086fabab74cc18cbbcfd79cd3340d422ef8a6c592700dcc7784225af9a3c02110000002f8d0de867000000000000000000

1 output(s) for total of 39.766573218000 dcy

stealth address amount amount idx
00: 30819e57bf3fe606d845941578464b888bb3077ad0c54f8d343103b3ade0428e 39.766573218000 730743 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": 358698, "vin": [ { "gen": { "height": 358688 } } ], "vout": [ { "amount": 39766573218, "target": { "key": "30819e57bf3fe606d845941578464b888bb3077ad0c54f8d343103b3ade0428e" } } ], "extra": [ 1, 142, 220, 8, 111, 171, 171, 116, 204, 24, 203, 188, 253, 121, 205, 51, 64, 212, 34, 239, 138, 108, 89, 39, 0, 220, 199, 120, 66, 37, 175, 154, 60, 2, 17, 0, 0, 0, 47, 141, 13, 232, 103, 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