Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4832e9773cc237c46b6e0002738915884c0732af740000d2e46d763bb21f8683

Tx prefix hash: e8df3cb12367447574b23d838e4d3e56b91ab6cfc43757a8463bc4b32ff12ea8
Tx public key: 6663a2cff79e55ae6f3fc8c792d21aa83d800562737e91f8550c5e9a1e125807
Timestamp: 1735512935 Timestamp [UCT]: 2024-12-29 22:55:35 Age [y:d:h:m:s]: 00:109:19:44:12
Block: 1186024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78302 RingCT/type: yes/0
Extra: 016663a2cff79e55ae6f3fc8c792d21aa83d800562737e91f8550c5e9a1e1258070211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 429187a962aab4446bc36f3f3e8768f5ea4cc5542f9c4fb286b29837c1879355 0.600000000000 1672499 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": 1186034, "vin": [ { "gen": { "height": 1186024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "429187a962aab4446bc36f3f3e8768f5ea4cc5542f9c4fb286b29837c1879355" } } ], "extra": [ 1, 102, 99, 162, 207, 247, 158, 85, 174, 111, 63, 200, 199, 146, 210, 26, 168, 61, 128, 5, 98, 115, 126, 145, 248, 85, 12, 94, 154, 30, 18, 88, 7, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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