Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df03005187835a0a449d2dd0cc2ea031e9315d3440246a701817d5d9323496c

Tx prefix hash: cba1953c1ecc0a3e1f2f212adc7e05058d4d88908d51415c0bd29f4ab495bd9d
Tx public key: 30290c8c1b3b24352316cdf9c903cfdb515248cd67760cec8be810db051eacdd
Timestamp: 1631586900 Timestamp [UCT]: 2021-09-14 02:35:00 Age [y:d:h:m:s]: 03:073:15:10:20
Block: 333337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828220 RingCT/type: yes/0
Extra: 0130290c8c1b3b24352316cdf9c903cfdb515248cd67760cec8be810db051eacdd02110000000f5d7cc334000000000000000000

1 output(s) for total of 48.252980739000 dcy

stealth address amount amount idx
00: ab3684ed8578037140552b2d2e04e21c6f8706e769cefa1d112a2778f3f6cf00 48.252980739000 687912 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": 333347, "vin": [ { "gen": { "height": 333337 } } ], "vout": [ { "amount": 48252980739, "target": { "key": "ab3684ed8578037140552b2d2e04e21c6f8706e769cefa1d112a2778f3f6cf00" } } ], "extra": [ 1, 48, 41, 12, 140, 27, 59, 36, 53, 35, 22, 205, 249, 201, 3, 207, 219, 81, 82, 72, 205, 103, 118, 12, 236, 139, 232, 16, 219, 5, 30, 172, 221, 2, 17, 0, 0, 0, 15, 93, 124, 195, 52, 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