Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb47864669fcb975f9a8c1c71b03d8516fb0f7f818a409b2c7716ca9eaccc0b5

Tx prefix hash: 8b6bc3930ec4d99dbc3c7e9ac639e70297e92e11d6aec54239231a46c6fee8a1
Tx public key: 0c60ca895f0cadd441eb7e39b7a460c5c32930f642fa64be52275ef95f7881c1
Timestamp: 1673207473 Timestamp [UCT]: 2023-01-08 19:51:13 Age [y:d:h:m:s]: 01:303:02:53:49
Block: 670477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477636 RingCT/type: yes/0
Extra: 010c60ca895f0cadd441eb7e39b7a460c5c32930f642fa64be52275ef95f7881c102110000000152542ceb000000000000000000

1 output(s) for total of 3.684997691000 dcy

stealth address amount amount idx
00: 017a7b9e8c53c36a46e2077757ce7dc5882973eb3bffd834492a09a9249cea70 3.684997691000 1111882 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": 670487, "vin": [ { "gen": { "height": 670477 } } ], "vout": [ { "amount": 3684997691, "target": { "key": "017a7b9e8c53c36a46e2077757ce7dc5882973eb3bffd834492a09a9249cea70" } } ], "extra": [ 1, 12, 96, 202, 137, 95, 12, 173, 212, 65, 235, 126, 57, 183, 164, 96, 197, 195, 41, 48, 246, 66, 250, 100, 190, 82, 39, 94, 249, 95, 120, 129, 193, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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