Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2339a1d06de4a768cbef22703b4dbd501f4816d5e398f5ddb25b533d957a6a

Tx prefix hash: 147fdd3971df972083d651e10f3de8f906312c4fa5e3bcf2c2728e4fa265dcb7
Tx public key: d8d82465ae06e105aeaaafb7be7693980310cf61bf7dc424e416fbaa5b93ee09
Timestamp: 1676901502 Timestamp [UCT]: 2023-02-20 13:58:22 Age [y:d:h:m:s]: 02:095:05:04:27
Block: 701133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589678 RingCT/type: yes/0
Extra: 01d8d82465ae06e105aeaaafb7be7693980310cf61bf7dc424e416fbaa5b93ee0902110000000475e3f0e9000000000000000000

1 output(s) for total of 2.916454655000 dcy

stealth address amount amount idx
00: 81b3ffa61f3094d972b07d02fa13d0049d1e059cb401e1d63e1a46fd1c21d870 2.916454655000 1144598 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": 701143, "vin": [ { "gen": { "height": 701133 } } ], "vout": [ { "amount": 2916454655, "target": { "key": "81b3ffa61f3094d972b07d02fa13d0049d1e059cb401e1d63e1a46fd1c21d870" } } ], "extra": [ 1, 216, 216, 36, 101, 174, 6, 225, 5, 174, 170, 175, 183, 190, 118, 147, 152, 3, 16, 207, 97, 191, 125, 196, 36, 228, 22, 251, 170, 91, 147, 238, 9, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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