Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395fb926c41df91bb30fa8351ed9653888b2903c3b5312f5a32beeff77b334be

Tx prefix hash: f3a19af159e08f5c27ff1e1d1577aae4a00f5c2b03b31ead46c123ab5cb8b898
Tx public key: b4ff27acb3c5bb3e83a433b716a666891203b817162f02d4c95afe20fdd5642a
Timestamp: 1728200268 Timestamp [UCT]: 2024-10-06 07:37:48 Age [y:d:h:m:s]: 00:171:05:02:32
Block: 1125539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122141 RingCT/type: yes/0
Extra: 01b4ff27acb3c5bb3e83a433b716a666891203b817162f02d4c95afe20fdd5642a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a83e3d9aefcbd88421f95e20afedb30de79b5ef7e06dd119c551e2ec05ef30f 0.600000000000 1608290 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": 1125549, "vin": [ { "gen": { "height": 1125539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a83e3d9aefcbd88421f95e20afedb30de79b5ef7e06dd119c551e2ec05ef30f" } } ], "extra": [ 1, 180, 255, 39, 172, 179, 197, 187, 62, 131, 164, 51, 183, 22, 166, 102, 137, 18, 3, 184, 23, 22, 47, 2, 212, 201, 90, 254, 32, 253, 213, 100, 42, 2, 17, 0, 0, 0, 5, 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