Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fda7dd1c398b987c530c408737ef119374a33234510e13d919d92c17267da18

Tx prefix hash: aa2d4001c898965502bcac89f9837436c63070cd38135463b776bf9d92757f20
Tx public key: cb9cf4f98db737cb5a2af200e93db3d8f43a37aacf176043d8cb64d95feaa9ba
Timestamp: 1648865375 Timestamp [UCT]: 2022-04-02 02:09:35 Age [y:d:h:m:s]: 03:032:04:08:47
Block: 471320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803365 RingCT/type: yes/0
Extra: 01cb9cf4f98db737cb5a2af200e93db3d8f43a37aacf176043d8cb64d95feaa9ba0211000000025eb576c5000000000000000000

1 output(s) for total of 16.841069154000 dcy

stealth address amount amount idx
00: b36faec872c47f2f36b9aa5fadaf78c2db79313c92db3dc3ddd7f0cded5c3115 16.841069154000 890636 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": 471330, "vin": [ { "gen": { "height": 471320 } } ], "vout": [ { "amount": 16841069154, "target": { "key": "b36faec872c47f2f36b9aa5fadaf78c2db79313c92db3dc3ddd7f0cded5c3115" } } ], "extra": [ 1, 203, 156, 244, 249, 141, 183, 55, 203, 90, 42, 242, 0, 233, 61, 179, 216, 244, 58, 55, 170, 207, 23, 96, 67, 216, 203, 100, 217, 95, 234, 169, 186, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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