Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00096e39d9ad50335e01ec1f90f464d8070c79439a92da63853acd7c0281dcb3

Tx prefix hash: ba09f2c535d44c3095e27ca596bee236c675a54cdc773a9b282ba8b0ce9cf5f6
Tx public key: bb7eaa7ecade1b93a70cf70c2198d7af6da8382a825d814a868aa49e5f2656f8
Timestamp: 1724541931 Timestamp [UCT]: 2024-08-24 23:25:31 Age [y:d:h:m:s]: 00:222:01:43:53
Block: 1095230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158555 RingCT/type: yes/0
Extra: 01bb7eaa7ecade1b93a70cf70c2198d7af6da8382a825d814a868aa49e5f2656f802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af7a15a6e59cbdf4fc4b30fea95c4a902f2e2c7a54d3ebdbb4f18b892eef4080 0.600000000000 1570385 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": 1095240, "vin": [ { "gen": { "height": 1095230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af7a15a6e59cbdf4fc4b30fea95c4a902f2e2c7a54d3ebdbb4f18b892eef4080" } } ], "extra": [ 1, 187, 126, 170, 126, 202, 222, 27, 147, 167, 12, 247, 12, 33, 152, 215, 175, 109, 168, 56, 42, 130, 93, 129, 74, 134, 138, 164, 158, 95, 38, 86, 248, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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