Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb0501e651fc79025d2c404b4c46384771d5c117b0ba384261aaa9fe2a5153e

Tx prefix hash: d52085d83c951f00d20d7c31e2eced6136660c3755dd51a952c7a40e4a766da9
Tx public key: a7da08053df00de3aa23de2ddcded679af190e42b5d9ed03bb0f40eb5c890026
Timestamp: 1582035004 Timestamp [UCT]: 2020-02-18 14:10:04 Age [y:d:h:m:s]: 05:349:03:49:28
Block: 67451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1400322 RingCT/type: yes/0
Extra: 01a7da08053df00de3aa23de2ddcded679af190e42b5d9ed03bb0f40eb5c890026021100000005724f989b000000000000000000

1 output(s) for total of 366.866151727000 dcy

stealth address amount amount idx
00: 95a04818a81a977aa888f32155f0b7a2aff90c2ad26c75ce03383d0ea9e36750 366.866151727000 124302 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": 67461, "vin": [ { "gen": { "height": 67451 } } ], "vout": [ { "amount": 366866151727, "target": { "key": "95a04818a81a977aa888f32155f0b7a2aff90c2ad26c75ce03383d0ea9e36750" } } ], "extra": [ 1, 167, 218, 8, 5, 61, 240, 13, 227, 170, 35, 222, 45, 220, 222, 214, 121, 175, 25, 14, 66, 181, 217, 237, 3, 187, 15, 64, 235, 92, 137, 0, 38, 2, 17, 0, 0, 0, 5, 114, 79, 152, 155, 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