Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc73cd3f6a36944b1d180c561e8c93e2b548815afb6cae60c282a499895802e

Tx prefix hash: e5f251eb21efeb829055be3092f4bd9c9b4756f7931685ce86235d2c17ab4be1
Tx public key: 334d308c8312d34fbf86eadc81e0304e0f2d3d0f6a59f3981264a71cc14f4d7d
Timestamp: 1577150930 Timestamp [UCT]: 2019-12-24 01:28:50 Age [y:d:h:m:s]: 04:318:06:55:17
Block: 30252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116716 RingCT/type: yes/0
Extra: 01334d308c8312d34fbf86eadc81e0304e0f2d3d0f6a59f3981264a71cc14f4d7d0211000000014ac5aa02000000000000000000

1 output(s) for total of 487.262992090000 dcy

stealth address amount amount idx
00: 49359383e2b6dec09871ebb81732c2582d6510b23fb4f093c79f88e01594ca2e 487.262992090000 49950 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": 30262, "vin": [ { "gen": { "height": 30252 } } ], "vout": [ { "amount": 487262992090, "target": { "key": "49359383e2b6dec09871ebb81732c2582d6510b23fb4f093c79f88e01594ca2e" } } ], "extra": [ 1, 51, 77, 48, 140, 131, 18, 211, 79, 191, 134, 234, 220, 129, 224, 48, 78, 15, 45, 61, 15, 106, 89, 243, 152, 18, 100, 167, 28, 193, 79, 77, 125, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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