Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49f1738d3334f48c3c4a3c909e3f080a6f7470cfde0d6c9849e023bc543135d

Tx prefix hash: 757bc331618e4efd00d486e5800fea4dc8a4e7eb54a1c849420408ae0fa578a8
Tx public key: 45679090a48cf7d2cf21c24b8a69b2a28c0bf3db000f15c1e04064b258b8c8f3
Timestamp: 1702935880 Timestamp [UCT]: 2023-12-18 21:44:40 Age [y:d:h:m:s]: 01:125:23:36:34
Block: 916083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351167 RingCT/type: yes/0
Extra: 0145679090a48cf7d2cf21c24b8a69b2a28c0bf3db000f15c1e04064b258b8c8f302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef5785eec4cbf3a937f9af070d6ef922abfabb765b27183adec5d48d91a6e58 0.600000000000 1373557 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": 916093, "vin": [ { "gen": { "height": 916083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef5785eec4cbf3a937f9af070d6ef922abfabb765b27183adec5d48d91a6e58" } } ], "extra": [ 1, 69, 103, 144, 144, 164, 140, 247, 210, 207, 33, 194, 75, 138, 105, 178, 162, 140, 11, 243, 219, 0, 15, 21, 193, 224, 64, 100, 178, 88, 184, 200, 243, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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