Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f4b21f79fb0f960d29b972a00330bacc382eec05ce6a6ab7b70db90126359f

Tx prefix hash: 08605dbb228331ab794d0b8b1c94160330d8a665e3870b50498866c539352959
Tx public key: db8ca261e9bf6b791a6bb00c65b3cfc5ba3b5018b1f269587bf47d578d9e9826
Timestamp: 1735339635 Timestamp [UCT]: 2024-12-27 22:47:15 Age [y:d:h:m:s]: 00:081:23:28:46
Block: 1184589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58408 RingCT/type: yes/0
Extra: 01db8ca261e9bf6b791a6bb00c65b3cfc5ba3b5018b1f269587bf47d578d9e9826021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ff731bbd184ae8a1af7983cf8af53fb054603e21bb5104c5df5cf127c52c15 0.600000000000 1671048 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": 1184599, "vin": [ { "gen": { "height": 1184589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ff731bbd184ae8a1af7983cf8af53fb054603e21bb5104c5df5cf127c52c15" } } ], "extra": [ 1, 219, 140, 162, 97, 233, 191, 107, 121, 26, 107, 176, 12, 101, 179, 207, 197, 186, 59, 80, 24, 177, 242, 105, 88, 123, 244, 125, 87, 141, 158, 152, 38, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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