Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1faf1ba003ca3b170fcfbfcf6e7b8446b0ad4284e56f871fe8605d3475d3128e

Tx prefix hash: 04d41b868cf32004aae60244b3d20c334bbe2e0d0dfe04d305a2b7f6362c2cd4
Tx public key: 41b9384b0ab624eae1aaa44aa776a5833e79dca364155037a96df80f8c6b1db7
Timestamp: 1738917171 Timestamp [UCT]: 2025-02-07 08:32:51 Age [y:d:h:m:s]: 00:287:15:48:44
Block: 1213961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203343 RingCT/type: yes/0
Extra: 0141b9384b0ab624eae1aaa44aa776a5833e79dca364155037a96df80f8c6b1db7021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e38d1fa1d9472ee475a989264d2cd5aaa807fbb8a5c535ee59a895c88990e11 0.600000000000 1700746 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": 1213971, "vin": [ { "gen": { "height": 1213961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e38d1fa1d9472ee475a989264d2cd5aaa807fbb8a5c535ee59a895c88990e11" } } ], "extra": [ 1, 65, 185, 56, 75, 10, 182, 36, 234, 225, 170, 164, 74, 167, 118, 165, 131, 62, 121, 220, 163, 100, 21, 80, 55, 169, 109, 248, 15, 140, 107, 29, 183, 2, 17, 0, 0, 0, 6, 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