Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd762d62fcc578f6c3f2ac9ddcbf61997ce0fde82e48199c303a97ba446edbd

Tx prefix hash: bd96302dd0fd78d83b675af462c09a1ed01fd06da9e5ed012c9702bdfe6a4101
Tx public key: 469009596a3b67fb6729c2113bff245dd069f6886a26a7f8cb10f4963704568a
Timestamp: 1727161775 Timestamp [UCT]: 2024-09-24 07:09:35 Age [y:d:h:m:s]: 00:196:16:26:54
Block: 1116933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140375 RingCT/type: yes/0
Extra: 01469009596a3b67fb6729c2113bff245dd069f6886a26a7f8cb10f4963704568a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dffc6e8a107971e7775c93f4efeafac1eef6b85e2069179a2a7ea5dd4fc0b048 0.600000000000 1597588 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": 1116943, "vin": [ { "gen": { "height": 1116933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dffc6e8a107971e7775c93f4efeafac1eef6b85e2069179a2a7ea5dd4fc0b048" } } ], "extra": [ 1, 70, 144, 9, 89, 106, 59, 103, 251, 103, 41, 194, 17, 59, 255, 36, 93, 208, 105, 246, 136, 106, 38, 167, 248, 203, 16, 244, 150, 55, 4, 86, 138, 2, 17, 0, 0, 0, 2, 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