Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59aa39df6f1d787545931ad9968272c1d8bcd9a1206f656c4fe9db82cf56702e

Tx prefix hash: cd65ec04e2925aebc876168242ecf3526ecc870f08f6346e6ffb1c74eaa1754e
Tx public key: 3b6a0ece8101f8db6e7f47b52b6e5dca0aad16c03d6a3570e7b47e39c794ab62
Timestamp: 1634645755 Timestamp [UCT]: 2021-10-19 12:15:55 Age [y:d:h:m:s]: 03:020:10:34:09
Block: 356158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 792665 RingCT/type: yes/0
Extra: 013b6a0ece8101f8db6e7f47b52b6e5dca0aad16c03d6a3570e7b47e39c794ab62021100000014fdc024ec000000000000000000

1 output(s) for total of 40.541621279000 dcy

stealth address amount amount idx
00: 1b2a4e9c8937286f5b7500168fd6c2e0ed9d74c573f4fd3c8356dcc465588fdb 40.541621279000 726796 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": 356168, "vin": [ { "gen": { "height": 356158 } } ], "vout": [ { "amount": 40541621279, "target": { "key": "1b2a4e9c8937286f5b7500168fd6c2e0ed9d74c573f4fd3c8356dcc465588fdb" } } ], "extra": [ 1, 59, 106, 14, 206, 129, 1, 248, 219, 110, 127, 71, 181, 43, 110, 93, 202, 10, 173, 22, 192, 61, 106, 53, 112, 231, 180, 126, 57, 199, 148, 171, 98, 2, 17, 0, 0, 0, 20, 253, 192, 36, 236, 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