Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f92025edb03a8d030eb494ce58ea912a766d514487fc9b44b97ea0faf81a795c

Tx prefix hash: a711ab7ab6cfde9d800d291ab476532dc8dc63321973181018fef176d356cc4d
Tx public key: c658a7e17f1634d903b4bab2dec1d41362a9f82102dfbd5e82a9091051b74a48
Timestamp: 1728151631 Timestamp [UCT]: 2024-10-05 18:07:11 Age [y:d:h:m:s]: 00:169:11:26:16
Block: 1125135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120907 RingCT/type: yes/0
Extra: 01c658a7e17f1634d903b4bab2dec1d41362a9f82102dfbd5e82a9091051b74a4802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb404f4367f6bd3fa63ecb4620f2ec5e03c3ff224e42e902a12612b42074fde4 0.600000000000 1607810 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": 1125145, "vin": [ { "gen": { "height": 1125135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb404f4367f6bd3fa63ecb4620f2ec5e03c3ff224e42e902a12612b42074fde4" } } ], "extra": [ 1, 198, 88, 167, 225, 127, 22, 52, 217, 3, 180, 186, 178, 222, 193, 212, 19, 98, 169, 248, 33, 2, 223, 189, 94, 130, 169, 9, 16, 81, 183, 74, 72, 2, 17, 0, 0, 0, 4, 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