Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98618d94d85f1f826a9783facf28fd3217c7ffc91b6ca0a1265c6c788db8c280

Tx prefix hash: 48dd8f3abbeb04f209b42840f9783bd63085b3de8e2888656486b6ccdc7eedf9
Tx public key: 91af651abfbcc0cba8dd34d41f7f5f7403f1fc9ee0765907ddffcdf1ae9f1404
Timestamp: 1716893459 Timestamp [UCT]: 2024-05-28 10:50:59 Age [y:d:h:m:s]: 00:319:21:06:53
Block: 1031812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228614 RingCT/type: yes/0
Extra: 0191af651abfbcc0cba8dd34d41f7f5f7403f1fc9ee0765907ddffcdf1ae9f14040211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caa4ae9425322e98a94d0da9f745d6b92d7dd48c7d7541cd94599c5f9361c637 0.600000000000 1500261 of 15

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": 1031822, "vin": [ { "gen": { "height": 1031812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa4ae9425322e98a94d0da9f745d6b92d7dd48c7d7541cd94599c5f9361c637" } } ], "extra": [ 1, 145, 175, 101, 26, 191, 188, 192, 203, 168, 221, 52, 212, 31, 127, 95, 116, 3, 241, 252, 158, 224, 118, 89, 7, 221, 255, 205, 241, 174, 159, 20, 4, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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