Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9576e67103692789c88ca2ef2089e36694c8bf79fd8a0e7e503264441d89a16

Tx prefix hash: cfc360d12c6f35ff8b196cec14426a11a9115fcb3f3e3703375a8dd6eb32e1a0
Tx public key: 8dcd9332bd1a40310eda0efd55ccbb6add813bde23a507280be3fc182cdf2c8c
Timestamp: 1707558423 Timestamp [UCT]: 2024-02-10 09:47:03 Age [y:d:h:m:s]: 01:059:12:33:26
Block: 954397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303590 RingCT/type: yes/0
Extra: 018dcd9332bd1a40310eda0efd55ccbb6add813bde23a507280be3fc182cdf2c8c0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f9e768f5daefbc9f7e23ec4e2c1d44484da27acd9f5c0430a2e960f5ee3b32 0.600000000000 1413677 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": 954407, "vin": [ { "gen": { "height": 954397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f9e768f5daefbc9f7e23ec4e2c1d44484da27acd9f5c0430a2e960f5ee3b32" } } ], "extra": [ 1, 141, 205, 147, 50, 189, 26, 64, 49, 14, 218, 14, 253, 85, 204, 187, 106, 221, 129, 59, 222, 35, 165, 7, 40, 11, 227, 252, 24, 44, 223, 44, 140, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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