Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9cbbff223ef0eabe1b7b9e0bc1185491146593551e3b334bf9d59e17f06c077

Tx prefix hash: efdc4ca308e807a78a8fbe66defc096f8b01f79f1d355f2e0628d3bfe4b7dc8d
Tx public key: 886a627e660e8a4aa64cba43ed4adb1a1c4afb29be4ed296a0a37177f34725d8
Timestamp: 1724122764 Timestamp [UCT]: 2024-08-20 02:59:24 Age [y:d:h:m:s]: 00:223:07:05:43
Block: 1091738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159446 RingCT/type: yes/0
Extra: 01886a627e660e8a4aa64cba43ed4adb1a1c4afb29be4ed296a0a37177f34725d8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a0beb30d9576de4413d598e9ea424c64d3c0a9b03cd9bf1b3675d176cd3d8b4 0.600000000000 1566371 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": 1091748, "vin": [ { "gen": { "height": 1091738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a0beb30d9576de4413d598e9ea424c64d3c0a9b03cd9bf1b3675d176cd3d8b4" } } ], "extra": [ 1, 136, 106, 98, 126, 102, 14, 138, 74, 166, 76, 186, 67, 237, 74, 219, 26, 28, 74, 251, 41, 190, 78, 210, 150, 160, 163, 113, 119, 243, 71, 37, 216, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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