Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b15c64365171a34e37a3e1fdb7fb8d0944e03a21a4264d25efb67a722d53cd

Tx prefix hash: 2bb56113ee4ea139c16f42541c568322869353056fc1a37b6664788d87ed87c4
Tx public key: 38976d883b2d2ea205e769aa6a64e2c0eb25e75a202435a476a70f311bc704d8
Timestamp: 1717457598 Timestamp [UCT]: 2024-06-03 23:33:18 Age [y:d:h:m:s]: 00:323:01:13:09
Block: 1036482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230877 RingCT/type: yes/0
Extra: 0138976d883b2d2ea205e769aa6a64e2c0eb25e75a202435a476a70f311bc704d80211000000034385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad827a545e02c9cfffc58452b186ba5f88b9327ab63fb9b8216360db0397f97 0.600000000000 1505009 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": 1036492, "vin": [ { "gen": { "height": 1036482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad827a545e02c9cfffc58452b186ba5f88b9327ab63fb9b8216360db0397f97" } } ], "extra": [ 1, 56, 151, 109, 136, 59, 45, 46, 162, 5, 231, 105, 170, 106, 100, 226, 192, 235, 37, 231, 90, 32, 36, 53, 164, 118, 167, 15, 49, 27, 199, 4, 216, 2, 17, 0, 0, 0, 3, 67, 133, 54, 42, 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