Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363c2a69f7ba7205f7c299584b9aeccaea2d8cecc026acdcafa630dc70604691

Tx prefix hash: c07e88c38bfce8db9d55d50914ec8f1d44fab9a8594cdb5a81241bc1c5a34671
Tx public key: 4240c09039653e4db934f57dad389a6726ce409c04c96f8ba4e6c8a3d33ac3bd
Timestamp: 1714960080 Timestamp [UCT]: 2024-05-06 01:48:00 Age [y:d:h:m:s]: 00:334:21:42:12
Block: 1015768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239396 RingCT/type: yes/0
Extra: 014240c09039653e4db934f57dad389a6726ce409c04c96f8ba4e6c8a3d33ac3bd0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ac3ea27fe189700eeed4ea0dc4dd4146130e2bbbb5fd21ddc7627fe634ebbb7 0.600000000000 1479211 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": 1015778, "vin": [ { "gen": { "height": 1015768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ac3ea27fe189700eeed4ea0dc4dd4146130e2bbbb5fd21ddc7627fe634ebbb7" } } ], "extra": [ 1, 66, 64, 192, 144, 57, 101, 62, 77, 185, 52, 245, 125, 173, 56, 154, 103, 38, 206, 64, 156, 4, 201, 111, 139, 164, 230, 200, 163, 211, 58, 195, 189, 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